Design Comments: A code specifying the major category of a Role as defined by HL7 vocabulary.

UsageNotes: http://www.hl7.org/v3ballot/html/infrastructure/vocabulary/RoleClass.htm

Rationale: Provides a means to identify Roles played by entities

Design Comments: This identification attribute supports capture of a healthcare identifier specific to the client. This identifier may be assigned jurisdictionally or by care facility.

UsageNotes: At least 1 client identifier must be present in the message

Rationale: Mandatory attribute supports unique identification of the client.

Design Comments: Indicates the status of the Client role (e.g. Active)

Rationale: Populated attribute supports the identification of the client

Design Comments: An interval of time specifying the period during which this record in a client registry is in effect, if such time limit is applicable and known

Rationale: Required attribute supports the identification of the client

Design Comments: A code that controls the disclosure of information about this patient encounter.

UsageNotes: Data in the EHR may at some point (and in some jurisdictions) be accessed directly by patients. Some health information may be deemed inappropriate for direct access by patients and requires interpretation by a clinician (e.g. prescription of placebos, analysis of certain psychiatric conditions, etc) Even where direct access by patient is not provided, there may need to be guidance to other providers viewing the record where care should be used in disclosing information to the patient. Non-clinical data (e.g. demographics) may need to be flagged as not for disclosure to patient and or next of kin. There may be professional policy and or legislative guidelines about when/if records may be flagged as not for direct disclosure.

Rationale: Populated attribute supports the business requirement to provide restricted access where required

Design Comments: The Person class contains identifying and demographic data elements for the focal person similar to those in the HL7 v2.x PID segment such as name, gender, date of birth, deceased indicator and time.

Rationale: Provides additional demographic data elements for the focal class IdentifiedEntity

Design Comments: Associates the IDENT role with a required observation which indicates the confidence value of the returned record(s).

Design Comments: An HL7 defined value representing the class or category that the Entity instance represents.

Examples: Person, Animal, Chemical Substance, Group, Organization

UsageNotes: http://www.hl7.org/v3ballot/html/infrastructure/vocabulary/EntityClass.htm

Rationale: Due to the extremely large number of potential values for a code set representing all physical things in the universe, the class code indicates both the subtype branch of the Entity hierarchy used as well as a high level classifier to represent the instance of Entity. This can be used to constrain the eligible value domains for the Entity.code attribute.

Design Comments: An HL7 defined value representing whether the Entity represents a kind-of or a specific instance.

Examples: 1 human being (an instance), 3 syringes (quantified kind) or the population of Indianapolis (kind of group)

UsageNotes: http://www.hl7.org/v3ballot/html/infrastructure/vocabulary/EntityDeterminer.htm

Rationale: An Entity may at times represent information concerning a specific instance (the most common), a quantifiable group with common characteristics or a general type of Entity. This code distinguishes these different representations.

Design Comments: Identifiers used for the focal person by other organizations are sent in the OtherIDs class. The other organization can be sent in the E_Organization Entity Class

Rationale: Provides the ability to capture additional client identifiers that are not healthcare specific

Design Comments: A code specifying the major category of a Role as defined by HL7 vocabulary.

Rationale: Provides a means to identify Roles played by entities

Design Comments: Other non-healthcare identifiers for the Client (e.g. Drivers License, RCMP, DND, Social Insurance Number)

Rationale: Mandatory attribute supports the identification of the client

Design Comments: A pan Canadian code further specifying the kind of Role such as Drivers License, RCMP, DND, Social Insurance Number

Rationale: Populated attribute supports the identification of the client

Design Comments: The Organization responsible for issuing the Other ID identified in the OtherIDs Role Class

Rationale: Supports the requirement to supply additional information regarding the assigning Organization of the OtherID

Design Comments: An HL7 defined value representing the class or category that the Entity instance represents.

Examples: Person, Animal, Chemical Substance, Group, Organization

UsageNotes: http://www.hl7.org/v3ballot/html/infrastructure/vocabulary/EntityClass.htm

Rationale: Due to the extremely large number of potential values for a code set representing all physical things in the universe, the class code indicates both the subtype branch of the Entity hierarchy used as well as a high level classifier to represent the instance of Entity. This can be used to constrain the eligible value domains for the Entity.code attribute.

Design Comments: An HL7 defined value representing whether the Entity represents a kind-of or a specific instance.

Examples: 1 human being (an instance), 3 syringes (quantified kind) or the population of Indianapolis (kind of group)

UsageNotes: http://www.hl7.org/v3ballot/html/infrastructure/vocabulary/EntityDeterminer.htm

Rationale: An Entity may at times represent information concerning a specific instance (the most common), a quantifiable group with common characteristics or a general type of Entity. This code distinguishes these different representations.

Design Comments: Unique identifier for the organization that assigned the non-healthcare identifier for the client.

Rationale: Mandatory attribute supports the identification of the organization assigning the identifier to the client

Design Comments: A name for the non-healthcare organization

Rationale: Populated attribute supports the identification of the organization assigning the identifier to the client

Design Comments: Each returned IdentifiedPerson can have an associated ObservationEvent reporting the confidence value (degree of certainty) and the name of the matching algorithm that resulted in that record's inclusion in the result set.

Rationale: Supports the business requirement to provide a confidence value associated with the identifiedEntity returned in the responsedistinguishes these different representations.

Design Comments: Supports the business requirement to identify type of confidence matching used i.e. the code would be the name for the algorithm for the confidence value

Rationale: Mandatory attribute supports confident identification of intended client

Design Comments: A real number value indicating the confidence of the query with regard to finding the intended target client i.e. the value would be the computed confidence value.

Rationale: Required attribute to provide information about success of query